Document breaking changes for MigrationsNotFound default throw and EFOptimizeContext removal#5282
Merged
AndriySvyryd merged 8 commits intopreview-3from Mar 5, 2026
Merged
Conversation
…MigrationsNotFound throw (#35218) Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Document breaking changes from recent EF Core pull requests
Document breaking changes for MigrationsNotFound default throw and EFOptimizeContext removal
Mar 4, 2026
AndriySvyryd
reviewed
Mar 4, 2026
entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
…new behavior text Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR documents two new EF Core 11 breaking changes in the existing breaking-changes.md page. The entries describe: (1) MigrationsNotFound event now throwing by default instead of logging informational message, and (2) removal of the redundant EFOptimizeContext MSBuild property.
Changes:
- Added a medium-impact breaking change entry for
MigrationsNotFounddefault throw behavior, including migration guidance usingConfigureWarnings - Added a low-impact breaking change entry for
EFOptimizeContextremoval, documenting the replacement propertiesEFScaffoldModelStageandEFPrecompileQueriesStage - Updated the summary table at the top of the page with links to both new entries
You can also share your feedback on Copilot code review. Take the survey.
Member
|
@copilot Also update the MSBuild integration page, noting that the changes only apply for 11+ |
…EF Core 11 Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
Contributor
Author
Updated the MSBuild integration page (
|
AndriySvyryd
reviewed
Mar 4, 2026
Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
…egration page Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
roji
approved these changes
Mar 5, 2026
entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md
Outdated
Show resolved
Hide resolved
Updated the mitigation section to clarify how to handle calling Migrate without migrations.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents two EF Core 11 breaking changes in
entity-framework/core/what-is-new/ef-core-11.0/breaking-changes.md:Low impact —
MigrationsNotFoundnow throws by default (efcore#35218):RelationalEventId.MigrationsNotFoundchanged fromInformationlog toErrorwith defaultThrowbehavior, consistent with thePendingModelChangesWarningtreatment from EF 9.0. Mitigation:Low impact —
EFOptimizeContextMSBuild property removed (efcore#35079): Redundant property removed;EFScaffoldModelStageandEFPrecompileQueriesStageare the sole controls for code generation.PublishAOT=trueenables generation automatically during publish.Also updates the MSBuild integration page (
entity-framework/core/cli/msbuild.md) to note thatEFOptimizeContextonly applies to EF Core 9-10 and was removed in EF Core 11.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.